home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Inside Mac Games Volume 7 #1
/
IMG Vol 7-1.iso
/
Shareware
/
Close Combat Utilities
/
CC Sold Mac
/
README.DOC
/
README.DOC
next >
Wrap
Text File
|
1996-08-10
|
9KB
|
200 lines
CCSOLD (Ver 1.0 Mac)
Close Combat Soldier Printer
Author: Bob „Limbo‰ Crane (rcrane@wsu.edu)
CCSOLD is a program that will write out the attributes and records of all
soldiers in the player‚s most recent campaign. It also writes out the team
leadership hierarchy.
Mac Installation and Use:
CC_Sold_Mac must be placed in the GAMES\MYOB folder under the Close
Combat directory. During campaign play,
CC stores American soldier information in the file ALUNITS and German
information in AXUNITS. These files are updated after a campaign battle is
completed and during replays of campaign scenarios. CCSOLD simply reads in
these files and outputs American force information in the file ALUNITS.DOC
and German information in AXUNITS.DOC. There are no command line
arguments. The player can then load these two text files into their
favorite word processor for viewing or printing. (Note: Line length of the
output exceeds 80 columns so I would not recommend printing the files
directly).
Output:
CC_SOLD‚s output is broken down into three different sections. The first
section lists the attributes of the soldier such as experience, morale,
weapon skills, etc. The second section lists the soldiers‚ record such as
number of tank kills, bravery deeds, etc. The last section lists the force
command hierarchy. Each section will be discussed in detail next.
Soldier Attribute Section:
Here is an example of partial output from the soldier attribute section:
Rank & Name Main Weapon Ldr Phy Men Exp Mor Cc Rif Sem Sub
BAR (0)
2nd Lt. Crane Carbine 91 52 41 83 89 40 65 69 57
Corporal Burris Garand 21 53 51 72 81 31 72 64 58
PFC Jacobs Garand-Gren 17 58 53 63 75 49 73 52 57
PFC Chandler Thompson 20 59 46 76 84 57 67 69 65
The section list soldiers sorted by their respective teams. Teams are
identified by their type and assigned a numerical index. For example, the
team above is a BAR crew (index #0) composed of 4 soldiers.
The first record indicates the soldier‚s rank and name. The American and
German ranks are given below:
Index American Ranks German Ranks
===== ================ ===============
0 Private Soldat
1 PFC Obersoldat
2 Corporal Gefreiter
3 Sergeant Obergefreiter
4 Staff Sergeant Unteroffizier
5 1st Sergeant Unterfeldwebel
6 1st Serg. 1st Cl. Oberfeldwebel
7 Master Sergeant Hauptfeldwebel
8 2nd Lt. Leutnant
9 1st Lt. Oberleutnant
10 Captain Hauptmann
11 Major Major
The second field lists the soldier‚s primary weapon. (Note: Some soldiers
in AV and AT gun crews do not man weapons.) In the example above, PFC
Jacobs carries a Garand capable of launching grenades.
The next fields list the soldier‚s attributes and weapon skills. Each is
scaled to range from 0 to 100. Here is a complete listing of the attribute
and skill fields:
Attributes:
Ldr = Leadership
Phy = Physical
Men = Mental
Mor = Morale
Skills:
CC = close combat (e.g., melee/bayonet)
Rif = rifle (e.g., Mauser, any hand held non-auto)
Sem = semi-auto gun (e.g., Garand, Carbine)
Sub = submachine gun(e.g., MP40, Thompson)
AtH = anti-tank hand-held weapon (e.g., Bazooka, Panzerfaust)
MG = machine gun (e.g., .30 cal MG, etc.)
Mor = mortar (e.g., 8cm Mortar, etc.)
Gun = Large Gun (e.g., 7.5cm L/48, 57mm L/50, etc.)
Gre = Grenade
Pis = Pistol (e.g., Colt .45, Walther P.38)
Soldier Record Section:
This section has a similar output as the Soldier Attribute section except
that it lists the number of heroic acts, kills, and medals a soldier has
received. The output replicates the detailed briefing screen in CC but it
also shows the number of half-track kills the soldier has. Here is a
complete listing of the fields:
Brav = Number of bravery acts
Cowd = Number of cowardly acts
TnkK = Number of tank kills
TrkK = Number of half-track kills (Currently not listed in CC)
GunK = Number of gun kills
American Medals:
MHon = Number of Medal of Honor medals received
DSC = Number of Distinguished Service Cross medals received
SiSt = Number of Silver Star medals received
BrSt = Number of Bronze Star medals received
ComB = Number of Combat Badge medals received
PHrt = Number of Purple Heart medals received
German Medals:
KnCr = Number of Knight‚s Cross received
CrGo = Number of Cross In Gold medals received
ICr1 = Number of Iron Cross 1st Class medals received
ICr2 = Number of Iron Cross 2nd Class medals received
AsBa = Number of Assault Badge medals received
WoBa = Number of Wound Badge medals received
Command Hierarchy Section:
The command hierarchy allows the user to determine who is in command of
who. Close combat currently makes use of this structure to compute
leadership bonuses. However, CC does not currently allow the user to see
the exact specification of the hierarchy. Here is an example output from
this section:
Company Commander, Captain Crane (BAR:0) / Heavy Rifle
Sergeant Nolan (Rifle:10)
1st Platoon Commander, 2nd Lt. Lanier (Rifle:1) / Light Rifle
Sergeant Pittman (Rifle:9), Sergeant Fisher (Recon:11)
1st Squad Commander, Sergeant Gray (81mm Mortar:4) / Heavy Support
PFC Milton (81mm Mortar:5), Private Gant (Bazooka:6)
2nd Squad Commander, Sergeant Stewart (BAR:7) / Heavy Rifle
Sergeant Vasques (Rifle:8)
3rd Squad Commander, Corporal Abel (M5A1:2) / Light Armor
UNKNOWN (M3 HT:3)
Each group of lines indicates a squad composed of one or more teams. The
squad commander is always listed first directly followed by one or more
teams under his command. For example, examine the squad commanded by
Sergeant Gray. Sergeant Gray is part of and commander of team #4, an 81mm
Mortar team. The first line also indicates that this squad is of the
„Heavy Support‰ type (see the SQUADS data file for more information).
Sergeant Gray is also in command of two other teams, team #5, another 81mm
Mortar team commanded by PFC Milton, and team #6, A bazooka team commanded
by Private Gant. In CC, Sergeant Gray has the opportunity to provide a
leadership bonus to teams #5 & #6 if he is within close proximity.
Indentation indicates that a squad is subordinate to another leader. For
example, Sergeant Gray‚s squad can receive a leadership bonus from 1st
Platoon Commander, 2nd Lt. Lanier. Finally, there is the Company commander
who can provide a leadership bonus to all of the teams. Sometimes a
commander or team name will come up as „UNKNOWN.‰ The most likely reason
for this is that commander or complete team was killed during the course of
previous battle.
The command hierarchy will allow the player to set up his/her units to
better take advantage of leadership bonuses. According to John Anderson of
Atomic, whether or not a team receives a leadership bonus is dependent on
the following formula:
effect = ( (leader's leadership * (leader's rank + 1) / Max Rank)
/ (range in meters / 20 + 1) );
So commanders are more effective if they have higher rank. They are also
very effective if within 20 meters of the subordinate team but not of much
value beyond 80 meters. A team only gets a leadership bonus if the
superior commander has a higher leadership value than the team‚s commander.
In addition, higher ranking commanders can never have a negative influence
over subordinate teams.
Limitations:
Unfortunately, CC_SOLD does not work with single scenarios. A?units files
get written only during the course of campaign play. CC_SOLD also is not
able to list the replacements available for the next scenario. CC_SOLD
does not work properly until the first scenario is completed (i.e., Off the
Beach, #1). CC_SOLD may not work if the player‚s campaign name is two or
more words (e.g., Von Excell). CC_SOLD is not an editor; it cannot
directly affect campaign play.
Future Plans:
John Thibeault (jthibeau@BayNetworks.com) has expressed an interest to
expand the program so that it tracks changes from one scenario to the next
during campaign play.
Acknowledgments:
My sincere thanks to John Anderson for providing me with information on how
to decode the unit data files. My thanks to Artur „Sky‰ Bergman and Claes
Jacobsson for compiling and testing the Mac version.
Bug Reports:
Send bug reports to Bob Crane (rcrane@wsu.edu). Please describe the
problem and send me a copy of your a?unit file from which the program
produced the error.
Legal Stuff:
This program is freeware and may not be used for commercial purposes. I am
not affiliated with Atomic in anyway and they will not provide support for
this product.